Data distribution by proxy

ABSTRACT

A communication device communicates with an originating device during an originating session and receives originating data from the originating device over a wireless communication link and then communicates with a receiving device during a receiving session and sends the originating data to the receiving device over a wireless communication link, such that the originating session and the receiving session occur at different times, and at least one of the sessions is an ad hoc communication session.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates generally to computer networks and, more particularly, to networks in which devices communicate in ad hoc fashion to transfer data.

2. Description of the Related Art

The phrase “computer network” generally refers to a collection of computers that communicate with each other over a shared network medium. The computers can comprise all manner of processing devices that can communicate using an appropriate network protocol, such as laptop computers, hand-held devices, personal digital assistants (PDAs), and the like. The shared medium for the network is often a sequence of wired connections, such as electrically conductive wiring or cabling. The medium can include optical fiber connections. The network shared medium can also comprise electromagnetic spectrum, such as communications using satellites, terrestrial towers, or other radio frequency (RF) connections.

Networks are useful for sharing data (including messages, audio information, video information, and documents in digital form) among online computers that comprise nodes of the network. When a user is “online”, the user is actively communicating over the network medium and is capable of communicating with one or more other computers that are also connected to the shared medium. Users who are not online (i.e., at computers that are not nodes of a network) cannot send or receive messages over the network. Computer users who are not online are generally said to be “offline”.

In the computer gaming context, it is desirable to share data such as game scores, player rankings, and tournament associations. For example, the U.S. patent application with publication No. US2002/0188360 to Muramori describes a system in which network game tournaments can be organized via registration of competitions. A player can play offline, without interaction with other players, and the offline player's individually-achieved score can be uploaded to the network later, when the player completes login to the network. In this way, players can get online and can then compare scores achieved by other players, view rankings, check tournament results, and the like. Any player with access to the appropriate network (such as the Internet) can participate in the network game tournament system. Networks with fixed resources, such as servers whose physical location does not change, will be referred to as fixed networks.

Mobile devices, such as network-enabled wireless handheld devices and cell phones, or laptop computers, can connect to a network at different places and at different times. They can operate offline and can connect online later, for network communications. In this document, mobile devices will also be referred to as wireless devices. Computing devices that are connected to a network through a wired or cable connector from the device itself will be referred to as wired devices.

Ad hoc networks (also called mesh networks) are created when a group of devices are in direct communication with each other at the same time (comprising a communication session) after a setup process in which the devices negotiate their network addresses for communication. That is, the members of the ad hoc network communicate with each other in real time, and the paths or links over which the ad hoc members communicate are established in a negotiation or setup procedure in which the members obtain a network address. The ad hoc network paths for communication are active while the members are online and in direct communication with each other, and otherwise the links do not exist. Thus, an ad hoc network is in contrast to a fixed network, in which network members communicate over network infrastructure through fixed network addresses. In any network environment, ad hoc or fixed, the communicating members can be wireless devices or wired devices.

Examples of fixed wireless networks include WLAN or “WiFi” networks that communicate through an access point over the IEEE 802.11 standard, as well as Bluetooth networks. For example, a laptop computer user can communicate wirelessly with a network access point such as a WiFi router, which itself might be connected to a high speed data line via copper coaxial cable, which ultimately travels over optical fiber to an Internet server. The network access point will typically assign a fixed network address to the laptop.

Alternatively, for an ad hoc network environment, two wireless devices may begin communications by broadcasting their presence and, upon detecting the presence of the other, the two may complete processing to establish wireless communications with each other. Such an arrangement is said to comprise a wireless ad hoc network. By means of such an ad hoc network, the two wireless devices can communicate with each other. When the devices break off communications, such as when one or both leave the vicinity of the other, or when one or both shut down, then the ad hoc network ceases to exist.

Some mobile devices are capable of multi-mode network operation. For example, some devices are capable of three modes of operation: (a) offline operation, in which a player might use the mobile device to play a game in solitude, without active connection to a network of any kind, (b) online operation to a fixed network infrastructure, such as where the user is connected to other players via a network (such as the Internet) and engages in interactive gaming communication with the other players, and (c) ad hoc network operation, in which users can be in direct communication with other players to establish an ad hoc network for gaming amongst the directly communicating players.

Although members of ad hoc networks can participate in data exchange between each other while they are connected together, they cannot exchange data with users to whom they are not actively connected. To effect a data exchange, the sending user and the receiving user must be actively communicating with each other at the same time. When they are actively communicating, they comprise an ad hoc network over which they can exchange data. Alternatively, if the sending user and the receiving user each have access to a fixed network, such as the Internet, the data can be exchanged over two links, or “hops”. First, the sending user can send data to the network, where it can be routed to a server or temporarily stored. The data can then be forwarded from the server over the Internet, or retrieved from storage, for reception at the receiving user.

Not all users who can connect to others via ad hoc networks can also connect to others via conventional networks. For example, access to the Internet generally requires that a user establish an appropriate service account with an access provider. Such service accounts generally are fee-based and require payment of access charges or subscription fees. Consequently, only those ad hoc users who have multi-mode devices and who pay for Internet access will be able to get online, notwithstanding their ability to communicate directly with others over an ad hoc network connection.

It would be desirable to permit greater flexibility in exchanging data among mobile ad hoc users who are not necessarily directly connected to intended recipients or to the online network.

Thus, there is a need for an improved, more efficient data exchange technique across offline, online, and ad hoc operating environments. The present invention satisfies this need.

SUMMARY

A communication device communicates with an originating device during an originating session and receives originating data from the originating device over a wireless communication link and then communicates with a receiving device during a receiving session and sends the originating data to the receiving device over a communication link, such that the originating session and the receiving session occur at different times, and at least one of the sessions is an ad hoc communication session. In this way, data is sent from the originating device to the receiving device through the communication device, automatically and without direct communication between the originating device and the receiving device. This enables a device to pass data over a fixed network, such as the Internet, without ever actually connecting to the fixed network, so long as the device can establish communication over an ad hoc network and pass the data to a communication device that can get the data to the fixed network. This provides more efficient data exchange across communication devices utilizing at least one communication hop over an ad hoc network, thereby comprising a “data by proxy” transfer.

The originating data can optionally be validated and authenticated, in separate processes or in a single combined operation, as desired. Thus, the communication device that receives the originating data can validate the data to ensure that the data is valid and can authenticate the data to ensure that the originating device is an authorized data source. If validation and authentication are successful, the communication device sends the validated and authenticated data to a receiving device over a wireless communication link. In this scenario, the data includes information that uniquely identifies the originating device that is the source of the data, and no direct communication takes place between the originating device and the receiving device.

If desired, the data exchange can be self-limiting, by providing for automatic limiting of data propagation. For example, the data can include an expiration time, and the communication device can decline to send the data if the expiration time has passed. The data can include time data that identifies an origination time at which the data was first generated, and the communication device can decline to send the data if the sent time is greater than a current time by at least a sending limit time value. The data can be checked against a message hop count value that is incremented with each sending of the message. The message is not sent if the hop count exceeds a predetermined limit value.

Many types of data can be sent using these techniques. For example, the data can include message data intended for a network device comprising a network node. In addition, the data can be generated by a network device comprising a network node, or the data can be generated by the communication device. The data can include status information for a software application. The data can include update information for a software application. If the data relates to a software application, then the software application can be installed on the communication device.

Other features and advantages of the present invention should be apparent from the following description of the preferred embodiment, which illustrates, by way of example, the principles of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic illustration of a computer ad hoc network constructed in accordance with the present invention.

FIG. 2 is a schematic illustration of data flow in an ad hoc network in accordance with the present invention.

FIG. 3 is a schematic illustration of multiple ad hoc network connections for operation in accordance with the present invention.

FIG. 4 is a flow diagram that illustrates processing at a communication device such as one of the communication devices illustrated in FIGS. 1, 2, 3.

FIG. 5 is a block diagram of a communication device constructed in accordance with the present invention.

FIG. 6 is a block diagram of an alternative communication device constructed in accordance with the present invention.

FIG. 7 is a flow diagram that illustrates processing at a communication device with authentication features.

DETAILED DESCRIPTION

FIG. 1 is an illustration of a computer system 100 constructed in accordance with the present invention. A wireless communication device comprising an originating device 102 exchanges data 104 to and from a receiving device 106 over a network 108. The originating device 102 can comprise any computing device that is capable of ad hoc wireless communication with one or more wireless-capable devices. Similarly, the receiving device 106 can comprise any computing device that is capable of ad hoc wireless communication with one or more wireless-capable devices. The network 108 comprises multiple communication links, or “hops”, utilizing one or more intervening communication devices, such that at least one of the hops is over an ad hoc network.

One of the devices 102, 106, 108 can comprise, for example, a server or router on a local area network (LAN) or on a wide area network such as the Internet. In accordance with an embodiment of the invention, the originating device 102 exchanges data with the receiving device 108 such that the originating device can pass data over a fixed network, such as the Internet, without ever actually connecting to the fixed network, so long as the originating device can establish communication over an ad hoc network and pass the data to a communication device that can get the data to the fixed network. The communication device can get the data to the fixed network because the communication device itself connects to the fixed network, or because the communication device communicates with one or more receiving devices such that the last device in a chain connects to the fixed network. This provides more efficient data exchange across communication devices utilizing at least one communication hop over an ad hoc network.

That is, the sending of data from the originating device 102 to subsequent communication devices over network hops 108 is continued from communication device to communication device in “hops” until the data is ultimately received at a receiving device 106. At each hop, the devices in communication will automatically detect the data to be sent and will implement the data transfer, if appropriate in view of any validation and authentication operations as discussed below. The receiving device 106 generally comprises a computer having a fixed network location, such as an Internet server or gateway computer, but can be a portable, hand-held wireless communication device such as a Web-enabled cell phone or PDA. The originating device 102 generally comprises a wireless device such as a portable game console, a Web-enabled PDA, a laptop computer, or a Web-enabled cell phone. The communication devices making up the network 108 can be similar devices. Thus, the originating device can exchange data with a receiving communication device over an ad hoc network, and the data can be repeatedly passed from communication device to communication device over ad hoc connections, until ultimately the data reaches a network node receiving device. In this way, the originating device can communicate with a network node receiving device without ever communicating directly with the receiving device, so that data propagation from the originating device can proceed while the originating device is offline. Thus, data is transferred across the network by proxy.

More particularly, in the context of the illustrated embodiments, the network 108 includes wireless communication devices such that at least one is adapted for communication with a fixed network node receiving device 106, so that an originating device can exchange data with the network node even without the originating device having network access to the network node. It should be understood that the originating device 102 is not in direct communication with the receiving device 106 when the data is received at the receiving device.

In FIG. 1, the data 104 is represented by a block adjacent the originating device 102, but it should be understood that the data 104 is sent over the network 108 to and from the receiving device 106. It also should be understood that the data 104 can comprise many different types of network messages. For example, the data 104 can comprise player scores, rankings, or tournament results for various game titles, or the data 104 can comprise software application update information, or the data 104 can comprise email messages.

As noted above, multiple data exchanges can take place between the device 102 that originates a data message (generates the data) and the last exchange, or “hop”, from a device of the network 108 to the network node receiving device 106. Each of the data exchanges can take place without user intervention. That is, each device is adapted to detect when it has data to be sent using the proxy technique described above. In response, such transfer will be initiated for a communication session. It should be understood that the data exchanges can be two-way. Thus, in general, the description provided herein will be from the perspective that the originating communication device 102 generates data for sending, but it should be understood that data can be received at the communication device 102 from another device, such as one of the member devices 108, or the network node 106.

The system 100 can provide validation and authentication services, if greater data security is desired. In that scenario, the originating data 104 that is sent over the network 108 includes information that uniquely identifies an originating device that is the source of the data. The communication device that receives the data and is to pass it along for the next hop over the network 108 will validate the data to ensure that the data is valid and will authenticate the data to ensure that the originating device is an authorized data source. The communication device will not send the data along if validation fails or if authentication fails. This ensures network integrity and provides more efficient data exchange across communication devices via ad hoc networks.

FIG. 2 provides a schematic illustration 200 of data flow in a network in accordance with an embodiment of the present invention. An originating device 202 generates data for sending. The originating device 202 sends the originating data to a communication device 204 over a wireless communication link. In this example, the originating device 202 and the communication device 204 comprise an ad hoc network. Thus, the two devices will establish communications with each other via a network address negotiation procedure, and will exchange data using a transfer protocol that is appropriate for the network. In the FIG. 2 embodiment, the communication device validates and authenticates the data, and if the data is validated and authenticated, the communication device will send the data along to a receiving device, designated Receiving Device A 206 in FIG. 2. The Receiving Device A will also perform the optional validation and authentication, and will send the data along to another device, and this process will occur repeatedly (indicated by the ellipses in FIG. 2) until the data reaches a Receiving Device B 208 and then a Receiving Device C 210, such that the Receiving Device C comprises a network node, such as a server on the Internet or other fixed network. Thus, each communication device will perform validation and authentication, as described further below, before sending along the data. In this way, multiple pair-wise device connections are made, from device 202 to communication device 204 and from communication device 204 to device 206 and so forth to the last device 210. Alternatively, the data can be sent from the originating device 202 to the communication device and then from the communication device 204 directly to a receiving device 210 in but two hops. In accordance with the invention, at least one of the communication hops is over an ad hoc network, thus providing network communications through devices where such access would otherwise be unobtainable.

FIG. 3 is a schematic illustration of a system diagram 300 that shows multiple scenarios for data exchange in accordance with the present invention. More particularly, FIG. 3 shows various ways in which data might be exchanged between Device A 304 a and a Node 399. In FIG. 3, the communication devices identified as Device A, Device B, Device C, and so forth through Device L are all identified as 304 with a respective letter suffix (a, b, c, . . . , l) to indicate that all the devices are capable of operation in accordance with the invention, meaning that all are capable of wireless communication with each other, and all can be members of respective ad hoc networks. A reference to devices without specifying a suffix letter will be understood to be a reference to the devices collectively. In the FIG. 3 embodiment, all the devices 304 will perform appropriate validation and authentication operations before forwarding received data.

Multiple communication scenarios are possible with the FIG. 3 system. For example, a first ad hoc network can be comprised of Device A 304 a, Device B 304 b, and Device C 304 c. Thus, Device A, Device B, and Device C can communicate with each other over wireless connections so that all may share data with each other. During such data exchanges, Device B can receive data from Device A, wherein the received data is intended for the network Node 399. After the three ad hoc network devices 304 a, 304 b, 304 c terminate their communications with each other, Device B 304 b can connect to a fixed network via the Node 399. In accordance with the invention, Device B will validate and authorize the data it received from Device A and, if such operations are successful, Device B will supply the Node 399 with the data. In this way, Device B will send along the data from Device A to the Node 399. It should be noted that Device A has not itself connected directly to the fixed network Node 399 or to any network of which the Node 399 is a member. That is, the data has been propagated from the originating device, Device A, to the network Node 399 while the originating device was offline.

In another scenario, Device A, Device B, and Device C can disconnect from each other, terminating their A-B-C ad hoc network, and then Device C can connect to a different ad hoc network that includes itself, Device D, Device E, Device F, Device G, and Device H. Connecting arrows for all the device connections are not shown for simplicity of illustration, but it should be understood that all members of the C-D-E-F-G-H ad hoc network can communicate with each other. In accordance with the invention, Device C 304 c, which received the data from Device A in the earlier ad hoc network, will perform validation and authentication, and then will send the data along to the members of its new ad hoc network. Thus, the communication devices of this C-D-E-F-G-H ad hoc network will share the data that Device C originally received from Device A. After a time, the devices of the C-D-E-F-G-H ad hoc network can disconnect from each other, terminating that ad hoc network. FIG. 3 shows that one of the devices, Device E 304 e, can connect to the Node 399. In accordance with the invention, the communication device 304 e will send the data to the Node 399, after validation and authentication. Thus, the originating data has made its way from Device A to Device C and from Device C to Device E, and then from Device E to the Node 399, a sequence of three links or hops. Once again, the data has proceeded from the originating Device A to the Node 399 without the originating device ever connecting directly to the network node 399 or to any network of which the Node 399 is a member.

FIG. 3 shows yet another ad hoc network that may be constituted, this one including Device F 304 f, Device G 304 g, Device H 304 h, and Device I 304 i. That is, some time after the C-D-E-F-G-H ad hoc network is terminated, communication devices can form up a F-G-H-I ad hoc network. Preferably, each of the devices F, G, and H will have previously received the data from Device C. Thus, the data will be exchanged with Device I upon creation of the F-G-H-I ad hoc network. None of the devices in the F-G-H-I ad hoc network is indicated as connecting to the Node 399, so the data is not sent on.

FIG. 3 indicates that another ad hoc network I-J-K is made up of corresponding communication devices: Device I 304 i, Device J 304 j, and Device K 304 k. Therefore, in accordance with the invention, Device I will have received the data from one or all of Device F, G, and H, which in turn will have received the data from Device C, which will have received the data in the A-B-C ad hoc network. In accordance with the invention, the data will be exchanged among the members of the I-J-K ad hoc network. FIG. 3 indicates that Device K is capable of direct communication with the Node 399. Therefore, when Device K performs a login with the Node 399, Device K will send the data to the Node, after validation and authentication. Thus, the data will have made its way from the A-B-C ad hoc network to the C-D-E-F-G-H network, from that network to the F-G-H-I network, from there to the I-J-K network, and from there directly to the Node 399. Once again, it should be noted that the data has been sent from Device A to the Node 399 without Device A ever directly connecting to a network of which the Node 399 is a part.

The last ad hoc network indicated in FIG. 3 is the K-L network, comprised of Device K 304 k and Device L 304 l. Thus, after the I-J-K ad hoc network is terminated, Device K can connect to Device L in a K-L ad hoc network. FIG. 3 indicates that both Device K and Device L can communicate directly with the Node 399. Therefore, each of them can provide the Node 399 with the data, upon respectively performing a login operation with the Node 399.

In this way, multiple communication devices 304 that operate in accordance with the present invention can cooperate to form successive ad hoc networks and can help exchange data between an originating device, Device A 304 a, and a receiving device, Node 399, all without the originating device ever connecting to a network of which the fixed Node is a member. In all of the data propagation scenarios illustrated in FIG. 3, data propagation after the initial sending from the first originating device (Device A) occurred while the originating device was offline. Thus, Device A was able to exchange data with the network Node 399 even though Device A was never in communication with the Node 399 and, in fact, was offline during all the scenarios described above.

FIG. 4 is a flow diagram that shows the sequence of operations performed by one of the communication devices constructed in accordance with the invention, for example, a device such as one of the devices 304 depicted in FIG. 3. The description of operations begins with receipt of originating data at a communication device. The originating data can comprise data created at the communication device or the originating data can be data received from an ad hoc network member. This data receipt operation is represented by the flow diagram box numbered 402. In the next operation 404, the communication device validates the data. The validation operation is an optional service that is performed to ensure that the originating data is in the proper format and can be correctly parsed to determine originating device, intended recipient, and data payload. For example, the validation operation might be used to verify that the machine identification number of the originating device is a valid number for the device type, to verify that the indicated receiving device is a proper Internet server, and to verify that the data payload relates to al legitimate application, such as comprising game tournament data related to an appropriate multiplayer network game, for which the receiving device is an Internet game server.

The next operation is for the communication device to perform authentication, as indicated at box 406. Authentication is an optional service that involves verifying that the originating device is authorized to be generating and sending the data. For example, access to the receiving device Internet game server might be limited to players who have enrolled in a tournament. If the data does not include information from which authorization can be confirmed, then the authorization process will fail. The authentication process can utilize a variety of schemes, such as public key cryptography or other types of encryption.

The validation 404 and authentication 406 are optional processes. The validation 404 and authentication 406 can be performed separately, or as a single combined operation, or one can be performed but not the other.

Next, indicated by the flow diagram box numbered 408, the communication device can perform optional filtering or editing tasks. For example, the originating data might include information that identifies when the data was first generated. If the communication device determines that the generation date of the data is beyond a time limit for data lifetime, then the communication device can decide to delete the message, or the device can send a failure message back to the originating device to indicate that the data will not be forwarded. Alternatively, the data might include an expiration date. The communication device can check a system clock value to determine a current date and time, which can be compared to the expiration date in the data. If the expiration date is passed, the communication device will delete the data or send a failure message. Thus, the communication device can perform a filtering operation.

Another optional operation 408 might comprise editing the data so as to update a message hop count. More particularly, the data can include a field comprising a message hop count that is incremented each time the data is passed from one ad hoc network to a different ad hoc network, or each time the data is passed from one communication device to another. The message hop count can be used to control or filter the number of times a data message is forwarded, or can be used to determine priority of sending or priority of storage, or other message handling decisions. Other message update or modification operations will occur to those skilled in the art, to ensure only appropriate data is propagated through the ad hoc communication system.

The filtering and editing tasks can be more effectively performed if the data includes message status information, such as a message hop count or a timestamp value that indicates when the data message was generated. The message hop count can comprise a field in each data message that can be checked and, if necessary, incremented by any receiving communication device. The timestamp value can be generated by the originating communication device upon generating the original data message. If desired, each device that handles (sends along) the data can append a timestamp value or can update the timestamp to indicate the message receipt time, message sending time, or other desired parameters. Thus, each communication device should perform appropriate operations to enable the desired filtering and editing options for data message handling.

The last operation 410 by the communication device is to send the data message to the next device in the ad hoc network of which it is currently a member or, if the communication device is communicating with a fixed network, to send the message to a fixed network node such as an Internet server or LAN node. In either case, at 410 the data is automatically sent without user intervention to initiate the sending.

As noted above, the communication devices shown in the block diagram of FIGS. 1, 2, and 3 can comprise a variety of devices. One of the possible devices is a laptop personal computer (PC) that is capable of wireless communications. FIG. 5 is a block diagram of a wireless PC communication device in the systems of FIG. 1, 2, and 3, illustrating the primary hardware components. Those skilled in the art will appreciate that the communication devices may all have a similar construction, or may have alternative constructions consistent with the capabilities described herein.

FIG. 5 shows an exemplary communication device 500 such as might comprise any of the communication devices in the systems of FIGS. 1, 2, and 3. The device 500 can comprise, for example, a wireless-enabled laptop computer or similar wireless-enabled computing device, such as a PDA, tablet computer, or the like. Each device 500 operates under control of a central processor unit (CPU) 502, such as a “Pentium” microprocessor and associated integrated circuit chips, available from Intel Corporation of Santa Clara, Calif., USA. A computer user can input commands and data from a keyboard and computer mouse 504, and can view inputs and computer output at a display 506. The display is typically a video monitor or flat panel display. The computer 500 also includes a direct access storage device (DASD) 508, such as a hard disk drive. The memory 510 typically comprises volatile semiconductor random access memory (RAM). Each computer preferably includes a program product reader 512 that accepts a program product storage device 514, from which the program product reader can read data (and to which it can optionally write data). The program product reader can comprise, for example, a disk drive, and the program product storage device can comprise removable storage media such as a magnetic floppy disk, a CD-R disc, a CD-RW disc, or DVD disc.

Each computer 500 can communicate over a wireless medium with the others in the ad hoc network 520 through a wireless network interface 518 that enables communication over a wireless connection 522 between the network 520 and the computer. The network interface 518 typically comprises, for example, a wireless Network Interface Card (NIC) that utilizes one of the IEEE 802.11 standards or other wireless network communication standards.

The CPU 502 operates under control of programming steps that are temporarily stored in the memory 510 of the computer 500. When the programming steps are executed, the computer performs its functions. Thus, the programming steps implement the functionality described in FIG. 4. The programming steps can be received from the DASD 508, through the program product storage device 514, or through the network connection 522. The program product storage drive 512 can receive a program product 514, read programming steps recorded thereon, and transfer the programming steps into the memory 510 for execution by the CPU 502. As noted above, the program product storage device can comprise any one of multiple removable media having recorded computer-readable instructions, including magnetic floppy disks and CD-ROM storage discs. Other suitable program product storage devices can include magnetic tape and semiconductor memory chips. In this way, the processing steps necessary for operation in accordance with the invention can be embodied on a program product.

Alternatively, the program steps can be received into the operating memory 510 over the network 520. In the network method, the computer receives data including program steps into the memory 510 through the network interface 518 after network communication has been established over the network connection 522 by well-known methods that will be understood by those skilled in the art without further explanation. The program steps are then executed by the CPU 502 thereby comprising a computer process.

It should be understood that all of the communication devices of the ad hoc network systems may have a construction similar to that shown in FIG. 5, so that details described with respect to the FIG. 5 device 500 will be understood to apply to all communication devices of the systems. It should be appreciated that any of the devices can have an alternative construction, so long as the device can communicate with the other communication devices over a network as illustrated in FIGS 1, 2, and 3 and can support the functionality described herein.

For example, with reference to FIG. 6, the communication devices 304 can comprise a wireless enabled computer entertainment system, such as a portable video game system 600 including devices such as the “Playstation Portable”™ (PSP) product from Sony Corporation of Japan. FIG. 6 is a block diagram of an exemplary hardware configuration of the portable video game system 600.

The video game system 600 includes a “PSP Engine” comprising a system controller/processor unit 602 that includes a core central processor unit, floating point processor, video processor, random access memory (RAM), graphics processor, and the like, all communicating over a core high-speed bus. Communicating with the PSP Engine 602 are various input, output, and system resource units. For example, a user control panel 604 permits a user to provide control inputs for data entry and gaming control. A USB interface 606 permits communication between the PSP Engine and external devices that are compatible with the Universal Serial Bus (USB) standard or other device-to-device communications, such as IEEE1394 (also referred to as “i.Link”, “Firewire”, or “Lynx”). A wireless interface 608 permits wireless communication between the device 600 and a network (WLAN), such as via the IEEE 805.11 standard. An interface for external media 610 supports a variety of storage media, such as flash memory, “Memory Stick”, and the like. A peripheral I/O block 612 provides interfaces for the system 600 with input/output units such as video displays, LCD devices, infrared devices (IrDA), joystick controllers, and the like. The I/O units may be integrated with the system or can be external, removable devices. The system 600 preferably includes support for extended memory 614, such that the system can communicate with extended memory cards (e.g., DRAM) and the like for supplementing the RAM of the system. The system preferably includes a Media Engine 620 for communications between the PSP Engine 602 and removable media for extended storage. The Media Engine is especially suited for interfacing with removable media intended for video data storage and retrieval, so that the interface incorporates high speed data transfer, large capacity, and reliable service. For example, data transfer speeds should be comparable to a LAN (in excess of 1 Mbps), and data capacity should be in excess of 1 GB.

The PSP Engine 602 includes a CPU that operates under control of programming instructions that are stored in RAM of the PSP Engine. The CPU is configured to process information and execute instructions in accordance with the programming instructions. The PSP Engine also includes a graphics processor unit (GPU) that is configured to perform drawing processes and formulate images in accordance with instructions received from the CPU. For example, the GPU may render a graphics image based on display lists that are generated by and received from the CPU. The GPU may include a buffer for storing graphics data. The GPU 610 outputs images to the peripheral I/O 612.

The wireless interface 608 is configured to enable operation of the communication device 600 in two wireless communication modes: an infrastructure mode and an ad hoc mode. In the infrastructure mode, the communication device can communicate with a wireless router or network access point, which typically are used for communication with a fixed network such as the Internet or a LAN. For example, the infrastructure mode can be used at a WiFi “hot spot” for network communications. In the ad hoc mode, the device 600 can communicate with other suitably configured wireless communication devices. The communication takes place directly with the other ad hoc network devices, in a peer-to-peer type of communication among the ad hoc network members. The particular ad hoc network will be established and identified via service set identification (SSID) information and channel information, which indicates a predetermined communications channel to be used among the ad hoc network members. Individual communication devices can be identified by a unique identification number, such as the conventional 48-bit MAC (media access control) address.

The external media 610 interface is configured to support a program reader, which can comprise, for example, an optical disk drive that accepts removable storage media such as a magnetic floppy disk, an optical CD-ROM disc, a CD-R disc, a CD-RW disc, a DVD disc, or the like. The external media includes various storage media to which the CPU 602 may write and store data, including memory cards that can be inserted and removed from the system 600.

As noted above, authentication and validation processes can be incorporated into the operation of the communication devices. FIG. 7 is a flow diagram that illustrates processing at a communication device with such operational features. Each of the devices 304 illustrated in FIG. 3 can be operated in a fashion similar to that described below, in addition to following the general sequence of operations described in connection with FIG. 4.

As illustrated in the first flow diagram box 702 of FIG. 7, when the communication device is first configured, a profile is created. The profile can include, for example, a user name, registration information, and the like. During the configuration, unique identifying parameters are set. The identifying parameters preferably involve two unique numbers that are generated. One number identifies the communication device, and the other number identifies the user of the device. These two numbers can be randomly generated, or derived from a hardware independent value (such as the MAC address of the device). These numbers are saved into the profile during the configuration operation.

Next, as represented by the next flow diagram box 704, a private/public key pair is generated and saved to the profile, as part of a private/public key encryption processing methodology. Those skilled in the art will be familiar with public key cryptography techniques, with which the devices 304 will be capable. After such initial configuration parameters are set, the communication device will, in the course of operation, establish communication with another device 304, referred to as the “next” device (see the discussion above involving FIG. 3). Thus, as represented by the flow diagram box numbered 706, the originating communication device detects the presence of another (next) device, or initiates a game with the another device.

The next operation, represented by box 708, is a data receipt operation such as described above, in which the communication device creates a data packet or message, or receives originating data from a sending device. As part of the authentication process, the communication device then performs a check to ensure that the data receipt operation does not result in accepting expired data or data that exceeds the permitted “hop” count (box 710). In the case where the communication device has any new data to generate (if for example the two devices have just played a game, and the originating communication device wants to send the new score), the communication device creates a data packet (message) for sending.

The data message contains, in plain text (unencrypted), data comprising: (a) a timestamp; (b) the unique User ID mentioned above; (c) the unique Machine Identifier described above; and (d) any Data that needs to be sent, such as a game score or any other desired data payload for the message. A message digest of the above information, encrypted with the private key saved in the profile of the originating device, is also included in the data message.

The message digest is a “hash value” generated by sending the plain text of a message through a “hash algorithm”. This hash value is then encrypted using the private key of the sender. When a person receives the message, the person can create a hash of the message, using the same hash algorithm as the sender. The person can then decrypt the sender's message digest using the sender's public key. If the hash that the receiving person generated matches that which the sender encrypted, then the receiving person knows that: (1) the sender originated the data (the hash was generated using a key only the sender had access to), and (2) the data has not been changed (the hash values matched, and it would not be mathematically feasible for two plain text messages to generate the same hash value.

Those skilled in the art will appreciate that the public key of the originating sender must be communicated to the receiving person, in accordance with operation of the private/public key cryptography methodology. The originating sender's public key can be sent to the receiving person at the time of establishing communications (box 706) or during a registration or sign-up operation, or in some other mechanism that is convenient to the person at the originating communication device and the receiving person.

In the next operation (box 712), the originating communication device provides a list of available messages to the next communication device (receiving person). The receiving device then responds with a list of data messages that are selected to be received. This operation is represented by the next box 714. If the receiving device includes a filter, then this operation would be performed automatically, without user intervention. For example, the filter may be set to reject all duplicate messages, or the filter could be set to reject all messages not addressed to the currently running software application. Other filter operation parameters can be set according to system requirements and desired features.

In the next operation, at box 716, the originating communication device sends all data packets of messages for which the receiving person has indicated a desire to receive. Upon receipt of the requested data, at box 718, the receiving device may authenticate the data sent, if the public key of the originating communication device is known. This will usually be the case, if the receiving device is receiving a message from a known server, or if the receiving device is a network node or other device receiving a message from a known client device. Finally, at box 720, the receiving device saves the data packets to storage of the receiving device.

The present invention has been described above in terms of a presently preferred embodiment so that an understanding of the present invention can be conveyed. There are, however, many configurations for the system and application not specifically described herein but with which the present invention is applicable. The present invention should therefore not be seen as limited to the particular embodiment described herein, but rather, it should be understood that the present invention has wide applicability with respect to network communications generally. All modifications, variations, or equivalent arrangements and implementations that are within the scope of the attached claims should therefore be considered within the scope of the invention. 

1. A method of operating a communication device for network communications, the method comprising: communicating with an originating device during an originating session and receiving originating data from the originating device over a communication link; communicating with a receiving device during a receiving session and sending the originating data to the receiving device over a wireless communication link; wherein the originating session and the receiving session occur at different times, and at least one of the sessions is an ad hoc communication session.
 2. A method as defined in claim 1, further comprising: validating the originating data to ensure that the originating data is valid; and authenticating the originating data to ensure that the originating device is an authorized data source; wherein the originating data includes information that uniquely identifies a source device as the source of the originating data, such that the communication device will not send the originating data if validation fails or if authentication fails.
 3. A method as defined in claim 2, wherein the originating data includes an expiration time, and the communication device will not send the data if the expiration time has passed.
 4. A method as defined in claim 2, wherein the originating data includes time data that identifies an origination time at which the originating data was first generated, and the communication device will not send the originating data if the time data indicates the origination time is greater than a current time by at least a sending limit time value.
 5. A method as defined in claim 2, wherein the originating data includes message data intended for a network device comprising a network node.
 6. A method as defined in claim 2, wherein the originating data is generated by a network device comprising a network node.
 7. A method as defined in claim 2, wherein the originating data is generated by the communication device.
 8. A method as defined in claim 2, wherein the originating data includes status information for a software application.
 9. A method as defined in claim 2, wherein the originating data includes update information for a software application.
 10. A method as defined in claim 9, wherein the software application is installed on the communication device.
 11. A method as defined in claim 2, wherein the communication device validates the originating data by determining that the originating data relates to a predetermined software application.
 12. A method as defined in claim 2, wherein the communication device validates the originating data by decoding validation information encrypted in the originating data.
 13. A method as defined in claim 2, wherein the communication device authenticates the originating device by determining that the originating device is an authorized source of data.
 14. A method as defined in claim 2, wherein the communication device authenticates the originating device by decoding authentication information encrypted in the originating data.
 15. A method as defined in claim 14, wherein the authentication information includes machine identification information of the originating device.
 16. A method as defined in claim 2, wherein the originating device is a network node, and the originating data is sent to the communication device only after the originating device has determined that the communication device has become an authorized device.
 17. A method as defined in claim 2, wherein the communication device selectively rejects the originating data in accordance with one or more filters that relate to the content of the data.
 18. A method as defined in claim 17, wherein the communication device will not send the originating data to the receiving device if the data has been rejected.
 19. A method as defined in claim 2, wherein the communication device receives the originating data from a sending device and then stores the data if it is not in communication with a device comprising a suitable receiving device.
 20. A method as defined in claim 19, wherein the communication device does not store the originating data if the communication device has insufficient available memory to store the data.
 21. A method as defined in claim 19, wherein the communication device determines if it has insufficient available memory and replaces an amount of stored data in the memory with the data sufficient to store the originating data in the memory.
 22. A method as defined in claim 19, wherein the originating data includes an expiration time, and the communication device will not store the data if the expiration time has passed.
 23. A method as defined in claim 19, wherein the originating data includes time data that identifies an origination time at which the data was first generated, and the communication device will not store the data if the sent time is greater than a current time by at least a sending limit time value.
 24. A method as defined in claim 2, wherein the originating data includes a message hop counter value, and the communication device increments the message hop counter value before sending the data to the receiving device.
 25. A method as defined in claim 24, wherein the receiving device comprises a network node, the originating data includes a data message identifier, and the receiving device will reject the data if the hop counter value of the received data is greater than the hop counter value of a previously received copy of the data having the same data message identifier.
 26. A method as defined in claim 2, wherein the originating device comprises a fixed network node.
 27. A method as defined in claim 1, wherein at least one of the communication device or receiving device is capable of wireless communication.
 28. A communication device comprising: a communications interface that supports data transfer between the communication device and a receiving device in an ad hoc manner; and a data store that stores data for transfer from the communication device to the receiving device; and a processor that executes operations such that the communication device communicates with an originating device during an originating session and receives originating data from the originating device over a communication link and communicates with the receiving device during a receiving session and sends the originating data to the receiving device over a communication link, wherein the originating session and the receiving session occur at different times, and at least one of the sessions is an ad hoc communication session.
 29. A communication device as defined in claim 28, wherein the originating data includes information that uniquely identifies an originating device that is the source of the originating data; and the processor validates the originating data to ensure that the data is valid and authenticates the data to ensure that the originating device is an authorized data source, and will not send the data if validation fails or if authentication fails.
 30. A communication device as defined in claim 29, wherein the originating data includes an expiration time, and the communication device will not send the data if the expiration time has passed.
 31. A communication device as defined in claim 29, wherein the originating data includes time data that identifies an origination time at which the data was first generated, and the communication device will not send the data if the sent time is greater than a current time by at least a sending limit time value.
 32. A communication device as defined in claim 29, wherein the communication device validates the originating data by determining that the data relates to a predetermined software application.
 33. A communication device as defined in claim 29, wherein the communication device validates the originating data by decoding validation information encrypted in the data
 34. A communication device as defined in claim 29, wherein the communication device authenticates the originating device by determining that the originating device is an authorized source of data.
 35. A communication device as defined in claim 29, wherein the communication device authenticates the originating device by decoding authentication information encrypted in the originating data.
 36. A communication device as defined in claim 29, wherein the communication device selectively rejects the originating data in accordance with one or more filters that relate to content of the data.
 37. A communication device as defined in claim 36, wherein the communication device will not send the originating data to the receiving device if the data has been rejected.
 38. A communication device as defined in claim 29, wherein the communication device receives the originating data from a sending device and then stores the data if it is not in communication with a device comprising a suitable receiving device.
 39. A communication device as defined in claim 38, wherein the communication device does not store the originating data if the communication device has insufficient available memory to store the data.
 40. A communication device as defined in claim 38, wherein the communication device determines if it has insufficient available memory and replaces an amount of stored data in the memory with data sufficient to store the originating data in the memory.
 41. A communication device as defined in claim 38, wherein the originating data includes an expiration time, and the communication device will not store the data if the expiration time has passed.
 42. A communication device as defined in claim 29, wherein the originating device comprises a fixed network node.
 43. A communication device as defined in claim 28, wherein the communication device is capable of wireless communication.
 44. A method of operating a communication device that is capable of ad hoc communication, the method comprising: receiving originating data from an originating device that generated the data in an original communication session, such that the communication device and the originating device comprise an ad hoc network, sending the originating data to a receiving device in a receiving communication session, such that the communication device and receiving device comprise an ad hoc network, and wherein the data includes information that uniquely identifies the originating device that generated the data; wherein the communication device is in direct communication with either the originating device or the receiving device while receiving the originating data and sending the originating data, but is not in communication with both devices at the same time.
 45. A method as defined in claim 44, wherein sending the originating data from the communication device to the receiving device comprises repeatedly sending the data from a next communications device to a different communications device one or more times until the data is received at a receiving device that is a fixed network node.
 46. A method as defined in claim 45, wherein the originating data further includes time data that identifies the time at which the originating device generated the data, and each communications device that receives the originating data will not send the data to a next communications device if the time data is greater than a current time by at least a limit value.
 47. A method as defined in claim 45, wherein the originating data further includes an expiration date, and each communications device that receives the data will not send the data to a next communications device if the expiration date has passed.
 48. A method as defined in claim 44, wherein the originating data further includes an expiration date.
 49. A method as defined in claim 48, wherein each communications device that receives the originating data will not send the data if the expiration date has passed.
 50. A method as defined in claim 44, wherein the originating data further includes time data that identifies the time at which the originating device generated the data.
 51. A method as defined in claim 50, wherein each communications device that receives the originating data will not send the data to a next communications device if the sent time is greater than a current time by at least a limit value.
 52. A method as defined in claim 44, wherein the originating data includes message data intended for a communications device comprising a network node.
 53. A method as defined in claim 44, wherein the originating data includes status information for a software application.
 54. A method as defined in claim 44, wherein the originating data includes update information for a software application.
 55. A method as defined in claim 54, wherein the software application is installed on the communications device.
 56. A method as defined in claim 44, wherein the originating data from the computing device further includes an expiration date.
 57. A method as defined in claim 47, wherein the subsequent device will not send the originating data if the expiration date has passed.
 58. A method as defined in claim 44, wherein at least one of the original communication session or the receiving communication session is a wireless communication session.
 59. A communication device that exchanges data over a computer network, the communication device comprising: a processor that executes a wireless communication process that enables the communication device to communicate with other devices over wireless connections; communication means for communicating with an originating device during an originating session and receiving originating data from the originating device over a communication link and communicating with the receiving device during a receiving session, and sending the originating data to the receiving device over a communication link, wherein the originating session and the receiving session occur at different times, and at least one of the sessions is an ad hoc communication session, such that sending the originating data to the receiving device occurs without direct communication between the originating device and the receiving device.
 60. A communication device as defined in claim 59, wherein the originating data includes information that uniquely identifies an originating device that is the source of the data, such that the communication device will not send the data if validation fails or if authentication fails.
 61. A communication device as defined in claim 60, wherein the communication means enables operation in an infrastructure mode and in an ad hoc mode, wherein in the infrastructure mode, the communication device can communicate with a fixed network access point and, in the ad hoc mode, the communication device can directly communicate with suitably configured wireless communication devices. 